SG-SST software for Colombian business groups: managing NITs, sites and responsibilities
A business group may share management, specialists and software without every company being the same employing entity. When choosing SG-SST software in Colombia, distinguish each entity’s NIT tax identifier, its sites and its management system responsibilities. This structure determines what is recorded, who decides and how results can be explained.
Decree 1072 of 2015 assigns SG-SST obligations to the employer and addresses coverage of its sites and workforce. A corporate dashboard supports oversight, but should not erase the identity of the company to which each activity and item of evidence belongs.
Map the group as it actually operates
Start with a list of entities, identifiers, sites, activities and responsible people. Add shared services and situations in which one person supports several companies. Distinguish physical location from legal entity: two companies may share premises while still needing clearly separated records and responsibilities.
The Explora entry on the OSH management system helps define each system’s scope. Use stable identifiers and effective dates in the data model. A later reorganisation should not retroactively assign every historical record to the newly created structure or remove its original context.
Separate responsibility, execution and consultation
A corporate specialist may prepare documentation for several entities, while approval and resource allocation belong to different managers. Evaluate software against this allocation of duties. Central team access should not become unrestricted access for every user simply because the companies form part of the same group.
Define permissions by entity and function. Identify who can administer structures, edit cases, submit evidence, approve decisions or view reports. Include temporary replacements, external consultants and removal of access at the end of an assignment. The same person may need different rights in two companies.
Share criteria without mixing evidence
The group can establish common templates, catalogues and criteria. Each entity needs the context of its implementation: covered people, sites, period, owners and decisions. A shared template does not automatically make an assessment, meeting record or work plan valid evidence for every company in the group.
The Explora entry on digital evidence in prevention explains traceability principles. To assess a solution, create a corporate reference document and two different local applications. Check how they are linked and what happens when one version changes while the other remains applicable.
Health information needs particularly clear boundaries. A requirement to consolidate a figure does not mean every department should access sensitive individual records. Define the data necessary for each purpose and review the applicable handling arrangements with the relevant responsible professionals before configuring broader access.
Consolidate indicators while keeping the detail
Agree definitions, periods and data sources before combining results. A group may want visibility over completed activities, overdue actions or training coverage. Reports should identify the included entities, show their contributions and distinguish missing data from an actual absence of incidents or outstanding work.
For rates and proportions, retain the numerators and denominators and apply the appropriate calculation to the combined data. Do not automatically average percentages from companies of different sizes. The Explora entry on OSH indicators helps prepare definitions that every responsible person can interpret consistently.
Test an entity change, not merely a site transfer
Consider an illustrative person whose relationship with one group company ends before a new relationship with another begins. The test should distinguish the new situation and preserve the historical documentation in its original context. Editing the company name on the current profile is not sufficient.
Also introduce a contractor serving two legal entities. Check that each contract, activity and piece of evidence has the correct scope, even where identification data can be shared. Reusing documentation requires consideration of its content, validity and relevance to the particular service rather than relying only on a matching supplier name.
Include these rules in the purchasing project
Make entity structures, permissions and consolidation demonstrable requirements. Ask how group expansion affects contracted scope and price. The guide to choosing SG-SST software in Colombia provides a framework for organising the assessment and recording unresolved questions before implementation begins.
Connect the structure to each SG-SST annual work plan. When considering Sabentis OSH software, describe your entities, sites and shared services. This supports a configuration that coordinates the group while preserving clear responsibilities for its constituent companies.
Checklist for adding a company to the system
Use a fictional onboarding exercise to establish where corporate configuration ends and the new company’s management begins. These five tests help reveal errors that an apparently clear organisation chart may conceal.
- Create two entities with identically named sites and check that documents, searches and notifications distinguish them without ambiguity.
- Give a specialist temporary access to the new entity and verify that access ends on the agreed date.
- Import a small sample of people with repeated identifiers and resolve matching issues before loading the full history.
- Produce a company report and a corporate report, then manually reconcile the records contributing to each result.
- Simulate corporate approval requiring local implementation and check who receives the outstanding task and who can close it.
Frequently asked questions
Can one software contract cover several NIT tax identifiers?
That depends on the contracted scope and demonstrated configuration. Distinguish the number of included legal entities from the number of users or sites. Request a proposal identifying the companies covered and the conditions for adding another, including migration, permissions and preservation of historical records.
How can I avoid duplicating someone working for two companies?
Separate personal identification from relationships with individual entities. A shared identifier can establish that records concern the same person, while each relationship retains its own dates and context. Check that merging identities does not mix training, responsibilities or documents belonging solely to one company.
What if two companies share an emergency exercise or inspection?
A coordinated activity can have common documentation. Explicitly identify participating entities and record the decisions belonging to each. In practice, both companies should be able to retrieve the shared origin without duplicating the finding or losing their separate owners and follow-up responsibilities.
How should companies of very different sizes be compared?
Show absolute results alongside relative measures using comparable definitions. Include population, period and data coverage. Combine this information with severity and exposure when deciding where to intervene: a small company should not disappear behind a group average or an aggregate completion percentage.
Legislation and consulted sources
- Decree 1072 of 2015. Colombia: employer duties and SG-SST organisation, supporting the definition of each entity’s scope. Spanish text.
- Law 1581 of 2012. Colombia: data protection, security and confidentiality principles relevant to access design. Spanish text.
Sources consulted on 6 October 2026.
